Providing a user with feedback regarding power consumption in battery-operated electronic devices

ABSTRACT

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for providing a user with feedback regarding power consumption in a battery-operated electronic device. In one aspect, a method performed by data processing apparatus includes identifying, using the data processing apparatus, usage of a hardware component of a battery-operated electronic device that includes the data processing apparatus, attributing the usage of the hardware component to the hardware component or to a software application that uses the hardware component, recording, using the data processing apparatus, a power consumption resulting from the usage, and presenting power consumption feedback to a user using the data processing apparatus. The power consumption feedback identifies the hardware component or the software application of the electronic device and the power consumption resulting from the usage.

RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.12/541,415 filed on Aug. 14, 2009. The disclosure of the priorapplication is incorporated herein by reference.

BACKGROUND

This specification relates to providing a user with feedback regardingpower consumption in a battery-operated electronic device.

Modern electronic devices provide a staggering array of functionality tousers. Battery-operated portable handheld electronic devices such astelephones, music players, PDA's, and game players can displayinformation on display screens, receive instructions from a user,communicate with other devices using wired and wireless data links, takedigital photographs, and process large volumes of digital data at speedsthat were unthinkable even a generation ago. Such functionality isimplemented using hardware components such as, e.g., display screens,keyboards and keypads, communications interfaces, digital dataprocessors, charge-coupled devices, and other integrated circuits thatcoordinate the operation of these and other hardware components. Thesevarious hardware components consume electrical power and thus help todeplete a battery or batteries in an electronic device.

SUMMARY

This document discusses systems, methods, and techniques by which abattery-operated electronic device, such as a smartphone or a netbookcomputer, can provide a user with information about which hardwarecomponents of the device consume, or are likely to consume, the mostpower on the device. For example, a device may display to the user alist of all power consuming hardware components or software applicationsthat are currently operating on the device, along with an indication ofhow much power each hardware component or software application isconsuming (either at the exact instant in time, or over a defined timeperiod). Such indications may be shown as an absolute value (e.g., inWatts or milli-watts) or as a relative value (e.g., in terms of thetotal power being consumed by all components or applications on thedevice, or of all components or applications that the user can currentlydisable). A graphical representation may also be provided so as to helpthe user make decisions about which components or applications todisable in order to save power. For example, bars graphs may be shownfor each component or application, where the length of the barapproximates the amount of power consumed by the component, or a piegraph may be shown in a similar manner, where the size of each slicerepresents the relative amount of power consumed by a correspondingcomponent. Displays like those just discussed may be shown in responseto an explicit user request (e.g., by the user navigating to a toolsmenu on a device or selecting a power management icon on a desktop orother area of a display on the device) or in response to other events,such as when the device falls below a certain level of power (e.g., 30%)at which a user can be expected to start shutting down non-essentialcomponents. In other instances, the system may automatically shut downcomponents or applications in a stepped manner at multiple differentbattery levels (based on a plan set for the system when it is shipped orby the user at a later time), or may provide suggestions to a user thatthe user can accept or reject. Such a system can also provide the userwith an estimate of the amount of time remaining on their battery if thecomponent or application is left on or turned off, or an estimate of theamount of time that will be added to the battery life by turning off acomponent or application.

Accordingly, in a first general aspect, a method performed by dataprocessing apparatus is described. The method includes identifying,using the data processing apparatus, usage of a hardware component of abattery-operated electronic device that includes the data processingapparatus, attributing the usage of the hardware component to thehardware component or to a software application that uses the hardwarecomponent, recording, using the data processing apparatus, a powerconsumption resulting from the usage, and presenting power consumptionfeedback to a user using the data processing apparatus. The powerconsumption feedback identifies the hardware component or the softwareapplication of the electronic device and the power consumption resultingfrom the usage.

This and other aspects can include one or more of the followingfeatures. The method can include monitoring usage of the component bythe application and converting the usage of the component into the powerconsumption that is attributed to the application. The component caninclude a wireless transceiver. The usage of the component can beconverted into the power consumption by identifying a range of signalstrengths during the usage of the wireless transceiver. The componentcan include a display. The usage of the component can be converted intothe power consumption by identifying a brightness state of the displayduring the usage.

The method can also include identifying a start of a new period andclearing a record of power consumption for the previous period inresponse. Information in the record of power consumption for theprevious period can be transferred into a long term record of powerconsumption in response to the identification of the start of the newperiod. Presenting the power consumption feedback to the user caninclude displaying a presentation that identifies applications andindications of amounts of power consumed by the identified applicationsand/or displaying a presentation that identifies different classes ofperiods and indications of average amounts of power consumed duringoperation in the different classes.

Other embodiments of this aspect include corresponding systems,apparatus, and computer programs, configured to perform the actions ofthe methods, encoded on computer storage devices.

In a second general aspect, a battery-operated electronic devices isdescribed. The battery-operated electronic device includes a battery, acollection of hardware components including a data processing unitconfigured to execute a plurality of different applications, and adisplay screen. The display screen presenting an accounting of powerconsumed by the different applications.

This and other aspects can include one or more of the followingfeatures. The electronic device can include a power measurement unit.The power measurement unit can be implemented in hardware and formeasuring a parameter characterizing power consumed by a first componentof the collection of components. The power measurement unit can includean ammeter. The display screen can present an accounting of powerconsumed by different components in the collection.

The electronic device can also include a data storage device. The datastorage device can store a structured collection of informationcharacterizing power consumed by the different applications during apresent period and a structured collection of information characterizingpower consumed by the different applications over a long term. The longterm is longer than the present period.

The data processing unit can be configured to monitor activitiesperformed using hardware components in the collection by the differentapplications and to calculate power consumption estimates attributableto respective of the different applications. The electronic device canalso include one or more persistent data storage devices storingconversion rules for estimating power consumptions by the differentapplications.

Other embodiments of this aspect include corresponding systems, methods,and computer programs.

In a third general aspect, a computer storage medium encoded with acomputer program is described. The program includes instructions thatwhen executed by data processing apparatus cause the data processingapparatus to perform operations. The operations include monitoringactivities performed by applications executed by a data processingapparatus of a battery-operated electronic device, estimating powerconsumptions for the activities, recording information characterizingthe power consumptions in association with information identifying theapplications that performed the activities, and presenting a user withan accounting of the estimated power consumption by the applications ona display screen of the battery-operated electronic device based on therecorded information.

This and other aspects can include one or more of the followingfeatures. The power consumptions for the activities can be estimated byidentifying that a first application holds a lock and attributingadditional power consumed during the lock to the first application. Thelock can maintain the hardware component in an active state. The lockcan be a wake lock. The power consumptions for the activities can beestimated by identifying that a second application holds the wake lockat the same time that the first application holds the wake lock andattributing additional power consumed during the wake lock in part tothe first application and in part to the second application.

The power consumptions for the activities can be estimated byidentifying that the first application requests that a hardware sensorbe active. The operations can include recording informationcharacterizing the power consumptions in association with informationidentifying the hardware components used by the applications to performthe activities.

Other embodiments of this aspect include corresponding systems,apparatus, and method for performing the operations.

The details of one or more implementations are set forth in theaccompanying drawings and the description below. Other features,aspects, and advantages will become apparent from the description, thedrawings, and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic representation of how a user can be provided withfeedback regarding power consumption in a battery-operated electronicdevice.

FIG. 2 is a schematic diagram of a battery-operated electronic device.

FIG. 3 is a flowchart of a process that can be performed by abattery-operated electronic device to provide a user with feedbackregarding power consumption.

FIG. 4 is a schematic representation of a record of the powerconsumption by different aspects of an electronic device.

FIG. 5 is a schematic representation of a system that implements ahardware-based approach for identifying and attributing usage of ahardware component of a battery-operated electronic device.

FIG. 6 is a schematic representation of a system that implements asoftware-based approach for identifying and attributing usage of ahardware component of a battery-operated electronic device.

FIG. 7 is a flowchart of a process that can be performed by abattery-operated electronic device to provide a user with feedbackregarding power consumption.

FIG. 8 is a schematic representation of a collection of estimates of thepower required by different components to perform different activities.

FIG. 9 is a flowchart of a process that can be performed by abattery-operated electronic device to provide a user with feedbackregarding power consumption.

FIG. 10 is a schematic representation of a long term record of powerconsumption by different applications, as well as a record the powerconsumption for the present period by different applications.

FIG. 11 is a schematic representation of how a user can be provided withfeedback regarding power consumption by aspects of a battery-operatedelectronic device.

Like reference numbers and designations in the various drawings indicatelike elements.

DETAILED DESCRIPTION

FIG. 1 is a schematic representation of one way that a user can beprovided with feedback regarding power consumption in a battery-operatedelectronic device 100. In general, device 100 visually shows to a user aplurality of hardware components or software applications operating indevice 100, along with a relative amount of power that each of thosecomponents or applications is consuming from the device's batterysystem.

Electronic device 100 can be, e.g., a telephone, music player, a PDA, agame player or other device that includes a display screen 105 thatpresents graphical images to a user. A portion of display screen 105includes a power consumption feedback presentation 110. Powerconsumption feedback presentation 110 presents a user with feedbackregarding power consumption by device 100 and can allow a user tounderstand how the battery power available to electronic device 100 hasbeen or is likely to be spent.

Feedback presentation 110 includes a period identifier 115 and acollection of account entries 120, 125, 130, 135, 140, 145, 150. Periodidentifier 115 includes text or other information 155 that identifiesthe period of time for which power consumption feedback is presented infeedback presentation 110. In the illustrated implementation,information 120 identifies that power consumption for a period of acertain duration (i.e., the “current period” of the last three hours and20 minutes) is provided. In other implementations, power consumptionfeedback can be provided for periods of time when, e.g., a certain useruses device 100, certain processes are running on device 100, or thelike.

Account entries 120, 125, 130, 135, 140, 145, 150 are records thatpresent an accounting of the power consumption of device 100. Differententries 120, 125, 130, 135, 140, 145, 150 can present an accounting ofdifferent aspects of the power consumption such as, e.g., the powerconsumption by one or more hardware components of device 100 or thepower consumption by one or more software applications executed on ofdevice 100. For example, in the illustrated implementation, accountentry 120 presents an accounting of the power consumption by displayscreen 105. Account entry 130 presents an accounting of the powerconsumption by a map application.

In the illustrated implementation, each account entry 120, 125, 130,135, 140, 145, 150 includes a title 160, a pictorial symbol 165, avisual indicium of power consumption 170, and a textual indicium ofpower consumption 175. Title 160 is text that identifies the aspect ofthe power consumption of device 100 for which an accounting is presentedin the respective entry. For example, title 160 in entry 140 identifiesthat entry 140 presents an accounting of power consumption by theoperating system of device 100. Title 160 in entry 135 identifies thatentry 135 presents an accounting of power consumption by an idle phoneof device 100.

Pictorial symbols 165 are pictorial representations of the aspects ofthe power consumption of device 100 for which accountings are presentedin the respective entries. For example, symbol 165 in entry 145represents that entry 145 presents an accounting of power consumption bytool applications of device 100. Symbol 165 in entry 125 identifies thatentry 125 presents an accounting of power consumption by the standbystate of a cellular communication system of device 100.

Each visual indicia 170 and textual indicia 175 presents an accountingof the power consumption by the aspects identified by title 160 andrepresented by symbol 165 in each account entry 120, 125, 130, 135, 140,145, 150. In the illustrated implementation, textual indicia 175 includetext that identifies the percent of the total power consumed bydifferent aspects. Visual indicia 170 are bars of different lengths. Thelengths of the bars are normalized to the highest power consumption byany aspect during the period identified by period identifier 115. Forexample, in the illustrated implementation, visual indicia 170 inentries 120, 125 are the same length and are each represent 23% of thetotal power consumption during the current period. In contrast, visualindicium 170 in entry 145 represents 10% of the total power consumptionduring the current period and is 10/23rds of the length of visualindicia 170 in entries 120, 125. In other implementations, thecharacteristics of visual indicia 170 can be normalized to, e.g., atotal power consumption during the period identified by periodidentifier 115.

FIG. 2 is a schematic diagram of another battery-operated electronicdevice 200. In general, the device 200 both provides a user withfunctionality and allows the user to obtain information about particularpower consumption by certain of the power-consuming components orapplications in the device 200.

Device 200 includes a housing 205 onto which a touch screen display 210is moveably mounted. Touch screen display 210 is moveable to expose andcover a keyboard 215. A portion of touch screen display 210 can includea power consumption feedback presentation 110 (FIG. 1). Powerconsumption feedback presentation 110 occupies all or a portion of touchscreen display 210.

Housing 205 houses a collection 220 of electronic hardware componentsthat cooperate to provide different functionality to the user.Electronic hardware component collection 220 includes a data processingunit 225, a display interface 230, a phone interface and component 235,a wireless interface and component 240, and a sensor interface andcomponent 245. Data processing unit 225, interface 230, and interfaceand components 235, 240, 245 can be implemented in electronic circuitry,in computer software, firmware, or hardware, or in combinations of theseand other elements.

Display interface 230 is a device that is configured to allow dataprocessing unit 225 to direct the presentation of information on touchscreen display 210. For example, display interface 230 can receiveinstructions for displaying content on touch screen display 210 fromdata processing unit 225. Display component 230 can translate thoseinstructions and cause the content to be appropriately presented ontouch screen display 210.

Phone interface and component 235 is a phone and an interface that isconfigured to allow data processing unit 225 to exchange data with thephone. Wireless interface and component 240 is a wireless transceiverand an interface that is configured to allow data processing unit 225 toexchange data with the wireless transceiver. Wireless interface andcomponent 240 can thus communicate with other devices on a wirelessnetwork. Sensor interface and component 245 is a sensor and an interfacethat is configured to allow data processing unit 225 to exchange datawith the sensor. The sensor can be, e.g., a hardware sensors such as anaccelerometer, a compass, a global positioning system, a digital camera,or the like.

Data processing unit 225 is a device that is configured to processdigital data. Data processing unit 225 can be, e.g., a generic purposedata processor that performs operations in accordance with theinstructions of application and other programs. Among the operationsperformed by data processing unit 225 is a consumption feedbackapplication 250.

Consumption feedback application 250 is a set of data processingactivities that are designed to create and accounting of the consumptionof power by different aspects of device 200 so that feedback regardingthat power consumption can be provided to a user.

During the performance of the activities of consumption monitor 250,data processing unit 225 can access conversion rules 255 and write toconsumption records 260. Conversion rules 255 and consumption records260 are stored in device 200, e.g., in one or more persistent datastorage devices. Various forms of persistent data storage may beprovided, e.g., fixed disk drives and/or solid state memory devices.Conversion rules 255 are rules for converting characteristics of theoperations performed by device 200 into a power consumption. Consumptionrecords 260 are historical records of the power consumed by differentaspects of the device and its operations. For example, consumptionrecords 260 can provide an accounting of the power consumption by thesame aspects identified and represented in account entries 120, 125,130, 135, 140, 145, 150 (FIG. 1).

FIG. 3 is a flowchart of a process 300 that can be performed by abattery-operated electronic device to provide a user with feedbackregarding power consumption. Process 300 can be performed by one or moredigital data processing devices that perform operations by executing oneor more sets of machine-readable instructions. For example, process 300can be performed by data processing unit 225 executing consumptionfeedback application 250 in device 200 (FIG. 2). Process 300 can beperformed in isolation or in conjunction with other digital dataprocessing operations.

The device performing process 300 can identify the usage of a hardwarecomponent of a battery-operated device at block 305. The usage of ahardware component can be identified, e.g., by monitoring power drawn bythe hardware component, by monitoring for activities performed byapplications with the component, or by monitoring for messages such asinstructions to the hardware component or descriptions of the activitiesfrom the applications themselves. For example, in the context of FIG. 2,the content of instructions sent from data processing unit 225 to one ormore of interface 230 and interface and components 235, 240, 245 can berelayed to consumption feedback application 250 so that it can identifyusage of the destination interfaces and components.

The device performing process 300 can attribute the power consumptionduring the usage of the component to an aspect of the device at block310. For example, power consumption can be attributed to a hardwarecomponent of the device (e.g., to a display screen, to a cell phone, toa transceiver, to a data processing unit, to a digital camera, or to anaccelerometer or other sensor) or power consumption can be attributed toan application executed by the device (e.g., to the operating systemsoftware, to a map application, to a game application, to mail or othermessaging application, to a web browser application, to a music or videoplayer application, or to a tool application).

In some implementations, power consumption during usage of the componentcan be attributed to multiple aspects of the device. For example, powerconsumed by an accelerometer during a game can be attributed to both theaccelerometer and to the game itself. As another example, the additionalpower that is consumed during a wake lock that is held by more than oneapplication can be attributed to all of the holding applications, asdescribed further below.

The device performing process 300 can record the attributed powerconsumption, e.g., in a persistent data storage device at block 315. Forexample, the device can record an estimate or a measurement of theamount of power that was consumed during the component usage inassociation with an identifier of the aspect to which that usage wasattributed in a data table or other data structure. Such recording canin effect create a historical record of the power consumption bydifferent aspects of the device.

The device performing process 300 also presents feedback regarding thepower consumption of the device to a user at block 320. For example, insome implementations, the system can present one or more of powerconsumption feedback presentation 110 (FIG. 1), and power consumptionfeedback presentations 1105, 1110 (FIG. 11) to present feedbackregarding power consumption by different aspects of an electronicdevice.

FIG. 4 is a schematic representation of a record 400 of the powerconsumption by different aspects of an electronic device. Record 400 canbe used as consumption records 260 in electronic device 200 (FIG. 2) andcan be formed during block 315 in process 300 (FIG. 3).

Record 400 includes a history by component table 405 and a history byapplication table 410. History by component table 405 is a datastructure that associates identifiers of the components to which powerconsumption is attributed in a column 415 with information describingthe amount of power attributed to those respective components in acolumn 420. History by application table 410 is a data structure thatassociates identifiers of the applications to which power consumption isattributed in a column 425 with information describing the amount ofpower attributed to those respective applications in a column 430. Theinformation stored in record 400 can be accessed by data processing unit225 during data processing activities such as consumption feedbackapplication 250 (FIG. 2).

FIG. 5 is a schematic representation of a system 500 that implements ahardware-based approach for identifying and attributing usage of ahardware component of a battery-operated electronic device. In additionto a data processing unit 225 that executes a consumption feedbackapplication 250, system 500 also includes a component interface 505, acomponent 510, and a power measurement unit 515. Component interface 505and component 510 are components of a battery-operated electronicdevice. For example, Component interface 505 and component 510 can be,e.g., display interface 230 and display 210 or any of interface andcomponents 235, 240, 245 (FIG. 2).

Power measurement unit 515 is a device configured to measure the powerconsumed by component 510. Power measurement unit 515 can be, e.g., anammeter that measures current flow from a battery 520 into a powerterminal 525 of component 510. The power consumed by component 510 canbe deduced or estimated from such a measurement based on the potentialprovided by battery 520. Power measurement unit 515 outputs a signal 530representative of the measured parameter.

Data processing unit 225 exchanges information 535 with componentinterface 505. Information 535 can include, e.g., output requests thatcomponent 510 perform specified operations and input informationcharacterizing the operation of component 510. Component interface 505itself exchanges corresponding information 540 with component 510.Information 540 can include, e.g., instructions for performing theoperations requested by data processing unit 225 or information fromcomponent 510 characterizing its operation.

Data processing unit 225 also receives signal 530 and conveysinformation describing both the source (i.e., the identity of a specificpower measurement unit 515 in a system with multiple units) and theinformation content of signal 530 to consumption feedback application250. Consumption feedback application 250 can use the informationrepresentative of the measured parameter to identify the usage ofcomponent 510. For example, when the power consumed by component 510increases, consumption feedback application 250 can identify thatcomponent 510 is being used. The description of the source of signal 530that can be used to attribute that power increase to component 510.

In some implementations, consumption feedback application 250 includesan application monitor module or other software mechanism forattributing the power increase at component 510 to specific applicationsexecuted by data processing unit 225. For example, consumption feedbackapplication 250 can monitor the amount of information displayed ondisplay screen 210 by different applications and attribute the powerusage by display screen 210 to those applications.

In some implementations, power measurement unit 515 measures powerconsumed by both component interface 505 and component 510. In suchcases, signal 530 represents combined measurements. The combinedmeasurements can be attributed to component 510 or to an applicationexecuted by data processing unit 225 in the same manner as individualmeasurements. Such combined measurements are particularly relevant wherethe power consumption by component interface 505 is not negligible incomparison to the power consumption at component 510.

FIG. 6 is a schematic representation of a system 600 that implements asoftware-based approach for identifying and attributing usage of ahardware component of a battery-operated electronic device. Consumptionfeedback application 250 includes an application monitor module 605 anda usage-to-power consumption converter module 610.

Application monitor module 605 is a set of computer program instructionsthat, when executed by data processing unit 225, cause data processingunit 225 to monitor the activities performed by data processing unit 225and other components for different applications. Application monitormodule 605 can, e.g., monitor the number of calculations performed bydata processing unit 225 when executing an application, monitor theamount of wireless traffic generated on a component by an application(e.g., traffic over either a cellular or a WI-FI network), monitor thehold and release of wake locks by different applications, monitor theusage of accelerometers or other sensors, and the like.

Application monitor module 605 is a set of computer program instructionsthat, when executed by data processing unit 225, cause data processingunit 225 to convert the activities performed by components for differentapplications into a power consumption. In general, the conversion canyield estimates of power consumption based on estimates amount of powerconsumed during an activity. For example, an estimate of the amount ofpower consumed per unit of a certain class of wireless traffic (e.g.,cellular traffic or WI-FI traffic) can be used to estimate the powerconsumed by the wireless traffic generated by an application. As anotherexample, an estimate of the cost to maintain an electronic device in awake state can be used to estimate the power consumed by an applicationthat locks the electronic device in the wake state.

FIG. 7 is a flowchart of a process 700 that can be performed by abattery-operated electronic device to provide a user with feedbackregarding power consumption. Process 700 can be performed by one or moredigital data processing devices that perform operations by executing oneor more sets of machine-readable instructions. For example, process 700can be performed by data processing unit 225 executing consumptionfeedback application 250 that includes a converter module 610 and anapplication monitor 605 (FIG. 6). Process 700 can be performed inisolation or in conjunction with other digital data processingoperations. For example, process 700 can be performed at blocks 305, 310in process 300 (FIG. 3) to identify usage of components and attributethe power consumed during such usage to different applications.

The device performing process 700 can monitor the activities that areperformed when executing different applications at block 705. Theactivities can be attributed to the executed application. For example,the computational requirements of processes used by an application canbe monitored and the process activities can be attributed to thatapplication. As another example, the network traffic generated whenexecuting a browser application can be monitored and the traffic can beattributed to the browser.

The device performing process 700 can convert the activities of thedifferent applications into a power consumption at block 710. Theconversion can yield estimates of the amount of power consumed by thedifferent applications and can be performed using rules for convertingthe activities into a power consumption, such as conversion rules 255(FIG. 2). The rules for converting the activities into a powerconsumption can be based on estimates of the power required by differentcomponents to perform different activities. In some implementations,these power consumption estimates can be a function of the operatingconditions of the components.

FIG. 8 is a schematic representation of a collection 800 of estimates ofthe power required by different components to perform differentactivities. Estimate collection 800 can express or be used inconjunction with conversion rules 255 in electronic device 200 (FIG. 2).

Estimate collection 800 includes one or more data structures that storeinformation that characterizes estimates of the power consumption bydifferent components under different operating conditions. In theillustrated example, estimate collection 800 includes a first wirelesscomponent table 805, a second wireless component table 810, an LCDscreen table 815, and an OLED screen table 820.

First wireless component table 805 includes a pair of columns 825, 830.Column 825 includes information identifying different ranges of signalstrength under which a first wireless transceiver component operates.Column 830 includes estimates of the power consumed by the transmissionor the reception of a signal by the first wireless component whenoperating under the corresponding range of signal strength in column825. The estimates can be expressed, e.g., per unit time that the firstwireless component is transmitting or receiving information or peramount of data that is transmitted or received by the first wirelesscomponent.

Second wireless component table 810 includes a collection of columns835, 840, 845. Column 835 includes information identifying differentranges of signal strength under which a second wireless transceivercomponent operates. Column 840 includes information identifying variousstates in which the second wireless transceiver component operates. Forexample, the information in column 840 can identify scanning states,multicast states, or other states of the second wireless transceiver.Column 845 includes estimates of the power consumed by the transmissionor the reception of a signal by the second wireless component whenoperating in the corresponding state in column 840 under thecorresponding range of signal strength in column 835. The estimates canbe expressed, e.g., per unit time that the second wireless component istransmitting or receiving information or per amount of data that istransmitted or received by the second wireless component.

Liquid crystal display (LCD) screen table 815 includes a pair of columns850, 855. Column 850 includes information identifying various states inwhich an LCD screen operates. For example, the information in column 850can identify different brightness levels of the LCD screen and itsbacklight. Column 855 includes estimates of the power consumed by LCDscreen when operating at the corresponding brightness in column 850.

Organic light-emitting diode (OLED) screen table 820 includes acollection of columns 860, 865, 870. Column 860 includes informationidentifying various states in which an OLED screen display operates. Forexample, the information in column 860 can identify different brightnesslevels of the OLED screen display. Column 860 includes informationidentifying the colors in which an OLED screen display. The powerconsumed by an OLED screen display is a function of the number and colorof illuminated pixels. Column 870 includes estimates of the powerconsumed by LCD screen when illuminating pixels of the correspondingcolor in column 865 at the corresponding brightness in column 850.

The following are examples of how the performance of activities ondifferent components can be converted into a power consumption that canbe attributed to that component or to an application.

Data Processing Unit 225:

In some implementations, the number of cycles executed by differentprocesses over a period of time (or a related parameter that reflectscomputational intensity) can be measured. The measurement result canthen be multiplied by a factor that embodies the power usage per unittime.

Wireless Transceivers:

The power consumed by a wireless transceiver is a function of the typeof transceiver and its signal strength. The data transmission andreception activities of each wireless transceiver in an electronicdevice can be assigned to a different bin according to an average signalstrength during those activities. In other words, there may be a totalof N*Y bins in an electronic device, wherein N is the number of wirelesstransceivers and Y is the number of signal strength ranges. For example,there may be five different ranges of signal strength for each wirelesstransceiver. Each time the data transmission and reception activities ofthe electronic device switch between bins, the data transmission andreception activity assigned to the former bin can be multiplied by anestimate of the power drawn by a transceiver operating within thecorresponding range of signal strength. This estimate of the powerconsumption can be attributed to one or both of:

-   -   the wireless transceiver and added to the amount of power        attributed to that wireless transceiver in a column 420 of table        405 (FIG. 4), and    -   the application for which the transmission and reception        activities were performed and added to the amount of power        attributed to that application in a column 430 of table 410        (FIG. 4).

Wake Lock Usage:

A wake lock is a lock that is held by an application to prevent a dataprocessing unit from entering a sleep or other power saving mode. As aresult, the data processing unit consumes power that would not have beenconsumed had the power saving mode been entered. Multiple applicationsmay hold a wake lock at the same time. In converting the holding of awake lock into a power consumption that can be assigned to anapplication, each request or release of a wake lock by an applicationcan be taken as a trigger demarcating the end of a period. The totalpower consumption for that period can be determined by multiplying theduration of the period by the power that was not saved as a result ofthe data processing unit not entering a power saving mode. This totalpower consumption can then be divided by the number of applications thatheld the wake lock during the period and the resulting quotient can beattributed to those applications in a column 430 of table 410 (FIG. 4).

Hardware Sensorssuch as accelerometers, compasses, digital cameras,global positioning systems, and the like:

Applications that use such sensors can be required to request that thedata from the sensor be delivered to the applications. In the absence ofa request, hardware sensors can remain inactive. The requests can beused as the basis for attributing power consumption by the sensor todifferent applications. Since multiple applications may request toreceive the data from a sensor at the same time, periods can bedemarcated based on requests and the total power consumption for eachperiod can be distributed among the applications that receive sensordata during each period.

LCD Screen and Backlight:

The display of graphics by an LCD screen and its backlight can beconverted into a power consumption by multiplying the duration of aperiod in which the LCD screen and its backlight are within a brightnessrange by an estimate of the power consumed within that brightness rangeper unit time.

$\begin{matrix}{P_{LCD} = {{\sum\limits_{i = 1}^{n}{t_{i}E_{i}}} + {{BE}{\sum\limits_{i = 1}^{n}t_{i}}}}} & {{Equation}\mspace{14mu} 1}\end{matrix}$

In implementations where the power consumption is be assigned to the LCDscreen and its backlight as components, Equation 1 can be used:

where “P_(LCD)” is the power consumption is be attributed to the LCDscreen and its backlight; “t_(i)” is the duration of a period “i;”“E_(i)” is an estimate of the excess power consumed by the LCD screenand its backlight during each period “i” (i.e., in excess of a baselineestimate “BE” of the power consumed by the LCD screen and its backlightat the lowest brightness); and there are “n” periods of operation by theLCD screen and its backlight.P_(LCD)=t_(i)E_(i)  Equation 2

In implementations where the power consumption by the LCD screen and itsbacklight is to be assigned to an application, Equation 2 can be used:

wherein “P_(app)” is the power consumption is be attributed to theapplication for a period “i” of a duration “t_(i)” and “E_(i)” is anestimate of the excess power consumed by the LCD screen and itsbacklight during period “i.”

OLED Display Screen:

The display of graphics by an OLED display screen can be converted intoa power consumption by counting the number of pixels at certain colorsand brightnesses and multiplying the number by an estimate of the powerneeded to maintain a pixel at that color and brightness. In someimplementations, the color, the brightness, or both the color andbrightness of groups of pixels can be averaged (e.g., by smoothingpixels using, e.g., bi-linear interpolation) and the average(s) can bemultiplied by an estimate of the power needed to maintain that group ofpixels at the average(s). Such estimates of power consumption can beattributed to the OLED display screen or to the application(s) thatpresent graphical images on the OLED display screen.

-   -   Phone Radio in an Idle State:

Maintaining the phone radio in an idle state can be converted into apower consumption by multiplying the duration of different periods inwhich the signal strength is within a certain range by an estimate ofthe power consumed within that signal strength range per unit time. Inimplementations where the power consumption is be assigned to the phoneradio as a component, Equation 3 can be used:

$\begin{matrix}{P_{idle} = {{\sum\limits_{i = 1}^{n}{t_{i}E_{i}}} + {{BE}{\sum\limits_{i = 1}^{n}t_{i}}}}} & {{Equation}\mspace{14mu} 3}\end{matrix}$

-   -   where “P_(idle)” is the power consumption is be attributed to an        idle phone radio as a component; “t_(i)” is the duration of each        idle period “i;” “E_(i)” is an estimate of the excess power        consumed by the phone radio during each idle period “i” (i.e.,        in excess of a baseline estimate “BE” of the power consumed by        the phone radio at the highest signal strength range); and there        are “n” idle periods of the phone radio within different signal        strength ranges.

Calling with the Phone Radio:

Calling with the phone radio can be converted into a power consumptionby multiplying the duration of different calling periods in which thesignal strength is within a certain range by an estimate of the powerconsumed within that signal strength range per unit time calling.

WI-FI transceiver (i.e., transceivers based on the IEEE 802.11standards):

The power consumed by a WI-FI transceiver is a function of signalstrength and state (e.g., scanning, multicast, etc.). The datatransmission and reception activities of a WI-FI transceiver can beassigned to a different bin according to an average signal strength ofthose activities in that state. In other words, there may be a total ofM*Z bins in an electronic device, wherein M is the number of signalstrength ranges and Z is the number of different states. Estimates ofthe power consumption can be attributed to one or both of:

the WI-FI transceiver itself and added to the amount of power attributedto that WI-FI transceiver in a column 420 of table 405 (FIG. 4), and

the application for which data transmission and reception activitieswere performed and added to the amount of power attributed to thatapplication in a column 430 of table 410 (FIG. 4).

Audio and Video Components such as headphones, dedicated decompressionhardware, and the like:

Applications that use audio and video components can be required torequest that the audio and video components be activated for use. In theabsence of a request, audio and video components can remain inactive.The requests can be used as the basis for attributing power consumptionby the audio and video components to different applications.

FIG. 9 is a flowchart of a process 900 that can be performed by abattery-operated electronic device to provide a user with feedbackregarding power consumption. Process 900 can be performed by one or moredigital data processing devices that perform operations by executing oneor more sets of machine-readable instructions. For example, process 900can be performed by data processing unit 225 executing a consumptionfeedback application 250 (FIG. 2). Process 900 can be performed inisolation or in conjunction with other digital data processingoperations. For example, process 900 can perform process 300 in order toprovide a user with feedback regarding power consumption in the presentperiod at block 925, as described further below (FIG. 3).

The device performing process 900 can determine whether a new period isstarting at decision block 905. Different periods can be delineated,e.g., by the electronic device being turned on or off, charging of theelectronic device being started or ended, the user of the electronicdevice switching, or by other occurrences. The start of a new period canbe identified, e.g., by sensing power-up or power down of the device,sensing the beginning or ending of battery charging, a change in theuser who is logged into the device, or the receipt of a manual triggerthat identifies the start of a new period.

In response to determining that a new period has started, the deviceperforming process 900 can transfer information describing the powerconsumption by different aspects of the electronic device during theperiod that ended into a long term record of power consumption at block910. The power consumption information for the present period can beadded to a longer term record of power consumption in order to documentto power consumption by different aspects of the device over extendedperiods. The actual term of the long term can be, e.g., a calendarperiod (e.g., a week, a month, or a year) or the lifespan of theelectronic device.

FIG. 10 is a schematic representation of a long term record 1005 ofpower consumption by different applications, as well as a record 1010the power consumption for the present period by different applications.

Long term record 1005 is a data structure that associates identifiers ofthe applications to which power consumption is attributed in a column425 with information describing the amount of power that has beenattributed to those respective applications over a long term in a column1020. Present period record 1010 is a data structure that associatesidentifiers of the applications to which power consumption is attributedin a column 1025 with information describing the amount of power thathas been attributed to those respective applications over the presentperiod in a column 1030. Either present period record 1010 or long termrecord 1005 can implement history by application table 410 (FIG. 4).

In transferring power consumption information from present period record1010 to long term record 1005, a data processing device can add thepower consumption attributed to an application in the present period tothe power consumption attributed to an application over the long term.For example, in the illustrated implementation, the power consumptionattributed to an application “app_(—)3” in the present period (i.e.,field 1035 in column 1030) can be added to the power consumptionattributed to that same application “app_(—)3” over the long term (i.e.,field 1040 in column 1020). As shown, power consumption will generallybe attributed to more applications over the longer term than in thepresent period.

Returning to FIG. 9, the device performing process 900 can also clear arecord describing the power consumption by different aspects of theelectronic device during the present period at block 915. For example,both the identifiers of the applications in column 1025 and theinformation describing the amount of power that has been attributed tothose respective applications in column 1030 can be cleared from apresent period record 1010 (FIG. 10).

The device performing process 900 can also reset a period timer inresponse to determining that a new period has started at block 920. Sucha period timer can be used to present text or other information 155 thatidentifies the period of time for which power consumption feedback ispresent in feedback presentation 110 (FIG. 1).

The device performing process 900 can also provide a user with feedbackregarding power consumption at block 925. For example, the device canperform process 300 (FIG. 3), with or without process 700 (FIG. 7) inorder to provide feedback regarding the power consumption in the presentperiod. As another example, the device can provide feedback regardingthe long term power consumption by aspects of the electronic device.

FIG. 11 is a schematic representation of how a user can be provided withfeedback regarding power consumption by aspects of a battery-operatedelectronic device 100.

Portions of display screen 105 include power consumption feedbackpresentations 1105, 1110. Power consumption feedback presentation 1105includes a collection of application identifiers 1115 that are eachassociated with a respective power rating indicium 1120. Applicationidentifiers 1115 identify applications that can be or have been executedon the electronic device. For example, application identifiers 1115 canidentify applications that are available to be downloaded from anapplication developer or supplier. Power rating indicia 1120 arepictorial symbols or other indicia that indicate the amount of powerconsumed by the identified applications.

The power consumption represented by power rating indicia 1120 can bedetermined in a number of ways. For example, in some implementations,the amount of power consumed by an application can be determined from along term record of the power consumption by that application, such aslong term record 1005 (FIG. 10). Power rating indicia 1120 can thusindicate the amount of power consumed by the identified applications asexecuted on that same electronic device. As another example, in someimplementations, power rating indicia 1120 can be determined fromrecords of the power consumption by that application on one or moreother devices. For example, a developer or supplier can collect recordsof power consumption by an application executed on a collectionelectronic devices. These collected records can then be used todetermine an average power consumed by the application and generate apower rating for the application.

Records of power consumption by applications are particularly relevantwhen applications can be developed by multiple developers. Inparticular, different developers may have different levels of expertiseand may develop similar applications that consume different amounts ofpower. When the amount of power consumed by the different applicationsis rated, a user can consider power consumption as a factor in decidingwhether to install or execute an application.

Power consumption feedback presentation 1110 includes a collection ofidentifiers 1125 of different classes of periods that are eachassociated with a respective power indicium 1130. Identifiers 1115identify different classes of periods of time when electronic device 100is in use. For example, a class of periods may occur at certain hoursduring the day (e.g., “noon-2 PM,” “2 PM-4 PM”), a class of periods mayoccur when electronic device 100 is used by specific users (“Jeanne,”“Julie”), or the like. Power indicia 1130 include text or other indiciathat indicates the average amount of power consumed during theidentified classes of periods. The power consumption represented bypower indicia 1130 can be determined in a number of ways. For example,in some implementations, a number different long term records of powerconsumption can be created, with each long term record associated with adifferent class. In response to a new period starting, the powerconsumption records for the former period can be transferred to therecords dedicated to periods of this class.

Various implementations of the systems, methods, and techniquesdescribed here can be realized in digital electronic circuitry,integrated circuitry, specially designed ASICs (application specificintegrated circuits), computer hardware, firmware, software, and/orcombinations thereof. These various implementations can includeimplementation in one or more computer programs that are executableand/or interpretable on a programmable system including at least oneprogrammable processor, which may be special or general purpose, coupledto receive data and instructions from, and to transmit data andinstructions to, a storage system, at least one input device, and atleast one output device.

These computer programs (also known as programs, software, softwareapplications or code) include machine instructions for a programmableprocessor, and can be implemented in a high-level procedural and/orobject-oriented programming language, and/or in assembly/machinelanguage. As used herein, the terms “machine-readable medium”“computer-readable medium” refers to any computer program product,apparatus and/or device (e.g., magnetic discs, optical disks, memory,Programmable Logic Devices (PLDs)) used to provide machine instructionsand/or data to a programmable processor, including a machine-readablemedium that receives machine instructions as a machine-readable signal.The term “machine-readable signal” refers to any signal used to providemachine instructions and/or data to a programmable processor.

To provide for interaction with a user, the systems, methods, andtechniques described here can be implemented on a computer having adisplay device (e.g., a CRT (cathode ray tube) or LCD (liquid crystaldisplay) monitor) for displaying information to the user and a keyboardand a pointing device (e.g., a mouse or a trackball) by which the usercan provide input to the computer. Other kinds of devices can be used toprovide for interaction with a user as well; for example, feedbackprovided to the user can be any form of sensory feedback (e.g., visualfeedback, auditory feedback, or tactile feedback); and input from theuser can be received in any form, including acoustic, speech, or tactileinput.

The systems, methods, and techniques described here can be implementedin a computing system that includes a back end component (e.g., as adata server), or that includes a middleware component (e.g., anapplication server), or that includes a front end component (e.g., aclient computer having a graphical user interface or a Web browserthrough which a user can interact with an implementation of the systems,methods, and techniques described here), or any combination of such backend, middleware, or front end components. The components of the systemcan be interconnected by any form or medium of digital datacommunication (e.g., a communication network). Examples of communicationnetworks include a local area network (“LAN”), a wide area network(“WAN”), and the Internet.

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

A number of embodiments have been described. Nevertheless, it will beunderstood that various modifications may be made without departing fromthe spirit and scope of the invention. For example, much of thisdocument has been described with respect to messaging and mappingapplications, but other forms of graphical applications may also beaddressed, such as interactive program guides, web page navigation andzooming, and other such applications.

In addition, the logic flows depicted in the figures do not require theparticular order shown, or sequential order, to achieve desirableresults. In addition, other steps may be provided, or steps may beeliminated, from the described flows, and other components may be addedto, or removed from, the described systems. Accordingly, otherembodiments are within the scope of the following claims.

1. A battery-operated electronic device comprising: a phone interface; abattery; a wireless transceiver; a display; a processor configured toexecute different software applications; one or more persistent datastorage devices; and memory storing instructions that when executed bythe processor cause the processor to perform operations for providinginformation regarding power consumption, the operations including:monitoring activities associated with each of the phone interface, thewireless transceiver, the display and the different softwareapplications; based on the monitoring, determining corresponding amountsof power consumed individually by each of the phone interface, thewireless transceiver, the display and the different softwareapplications; storing, using the one or more persistent data storagedevices, a first structured collection of information characterizingpower consumed by the different software applications during a presentperiod, wherein the one or more persistent data storage devices store asecond structured collection of information characterizing powerconsumed by the different software applications over a long term period,the long term period being longer than the present period; displaying,using the display, individual power consumption information for each ofthe phone interface, the wireless transceiver, the display and thedifferent software applications based on the amounts determined by theprocessor; and displaying, using the display, a presentation thatidentifies different classes of periods and indications of averageamounts of power consumed by the different software applications in thedifferent classes of periods.
 2. The battery-operated electronic deviceof claim 1, further comprising a power measurement unit operable tomeasure power consumed by one or more of the phone interface, thewireless transceiver and the display.
 3. The battery-operated electronicdevice of claim 1 comprising a power measurement unit operable toestimate the amounts of power consumption based on one or more measureparameters.
 4. The battery-operated electronic device of claim 3 whereinthe power measurement unit is operable to estimate at least some of theamounts of power consumption based at least in part on one or more ofcurrent flow from the battery into a power terminal, an average signalstrength of the transceiver, a duration of a period in which the displayscreen is within a particular brightness range, or a number of pixels inthe display screen at certain colors and brightness.
 5. Thebattery-operated electronic device of claim 1 wherein the display screendisplays absolute values of the respective amounts of power consumedindividually by at least some of the phone interface, the wirelesstransceiver, the display or the software applications.
 6. Thebattery-operated electronic device of claim 1 wherein the display screendisplays relative values of the respective amounts of power consumed byat least some of the phone interface, the wireless transceiver, thedisplay or the software applications.
 7. The battery-operated electronicdevice of claim 1 wherein the display screen displays graphicalindications of the respective amounts of power consumed by at least someof the phone interface, the wireless transceiver, the display thesoftware applications.
 8. A method performed by a battery-operatedelectronic device, the method comprising: determining by the electronicdevice a respective amount of power consumed individually by each of aplurality of hardware components and software applications in theelectronic device; presenting on a display unit of the electronic deviceseparate power consumption information for at least some of theindividual hardware components and software applications, whereinpresenting power consumption information includes providing on thedisplay unit a list of power consuming hardware components and softwareapplications that currently are operating on the electronic devicetogether with an indication of how much power each such hardwarecomponent and software application is consuming; storing a structuredcollection of information characterizing power consumed by the softwareapplications during a present period; storing a structured collection ofinformation characterizing power consumed by the software applicationsover a long term period, the long term period being longer than thepresent period; and displaying on the display unit a presentation thatidentifies different classes of periods and indications of averageamounts of power consumed by the software applications during operationin the different classes of periods.
 9. The method of claim 8 includingproviding on the display unit an indication of how much power each suchhardware component and software application is consuming at a particularinstant in time.
 10. The method of claim 8 including providing on thedisplay unit an indication of how much power each such hardwarecomponent and software application is consuming over a defined period oftime.
 11. The method of claim 8 wherein presenting power consumptioninformation on the display unit occurs in response to an explicit userrequest.
 12. The method of claim 8 wherein presenting separate powerconsumption information on the display unit occurs when a level of powerfor the electronic device falls below a specified level.
 13. The methodof claim 8 including monitoring activities performed by the hardwarecomponents and converting the activities performed by the componentsinto corresponding estimates of power consumption.
 14. A non-transitorycomputer-readable medium encoded with a computer program comprisinginstructions that, if executed, operate to cause an electronic device toperform operations comprising: monitoring, by the electronic device,activities associated with each of a phone interface, a wirelesstransceiver, a display and different software applications; based on themonitoring, determining by the electronic device, corresponding amountsof power consumed individually by each of each of the phone interface,the wireless transceiver, the display and the different softwareapplications; storing, using one or more persistent data storagedevices, a first structured collection of information characterizingpower consumed by the different software applications during a presentperiod, wherein the one or more persistent data storage devices store asecond structured collection of information characterizing powerconsumed by the different software applications over a long term period,the long term period being longer than the present period; displaying,using the display, individual power consumption information for each ofthe phone interface, the battery, the wireless transceiver, the displayand the different software applications based on the amounts determinedby the electronic device, displaying, using the display, a presentationthat identifies different classes of periods and indications of averageamounts of power consumed by the different software applications in thedifferent classes of periods.
 15. The medium of claim 14 includingdisplaying an indication of how much power each of the phone interface,the battery, the wireless transceiver, the display and the differentsoftware application is consuming at a particular instant in time. 16.The medium of claim 14 including displaying an indication of how muchpower each of the phone interface, the battery, the wirelesstransceiver, the display and the different software application isconsuming over a defined period of time.
 17. The medium of claim 14wherein displaying the individual power consumption information on thedisplay unit occurs in response to an explicit user request.
 18. Themedium of claim 14 wherein displaying the individual power consumptioninformation on the display unit occurs when a level of power for theelectronic device falls below specified level.
 19. The medium of claim14 including instructions that, when executed, operate to cause theelectronic device to display on the display unit a presentation thatidentifies different classes of periods and indications of averageamounts of power consumed during operation in the different classes. 20.The medium of claim 14 including instructions that, when executed,operate to cause the electronic device to monitor activities performedby each of the phone interface, the battery, the wireless transceiverand the display and convert the activities performed by the componentsinto corresponding estimates of power consumption.
 21. A mobile devicecomprising: electronic hardware components including a wirelesstransceiver, a display screen, and a data processing unit configured toexecute different software applications; and one or more persistent datastorage devices; wherein the data processing unit monitors powerconsumption in the mobile device and attributes amounts of powerconsumed individually by each of the hardware components and differentsoftware applications, and wherein the display screen presents powerconsumption feedback information separately for each of the hardwarecomponents and the different software applications based on the amountsattributed by the data processing unit, wherein the data processing unitstores in the one or more persistent data storage devices a firststructured collection of information characterizing power consumed bythe different software applications during a present period and a secondstructured collection of information characterizing power consumed bythe different software applications over a long term period, the longterm being longer than the present period, and wherein the displayscreen presents information that identifies different classes of periodsand indications of average amounts of power consumed during operation inthe different classes of periods.
 22. The mobile device of claim 21wherein the power consumption feedback information includes bothgraphical indicators of amounts of power consumed and textual indicatorsof the amounts of power consumed.
 23. The mobile device of claim 21including: a measurement device to measure a characteristic associatedwith power consumption for each hardware component; wherein the dataprocessing unit is operable to deduce or estimate the power consumptionfeedback information based on measurements by the measurement device.24. The mobile device of claim 23 wherein the data processing unit isoperable to measure a parameter that reflects computational intensityand to determine at least one of the power consumption estimates basedon the measured parameter.
 25. The mobile device of claim 21 wherein thedata processing unit is operable to determine at least one of the powerconsumption estimates based on an average signal strength.
 26. Themobile device of claim 21 wherein the data processing unit is operableto determine at least one of the power consumption estimates based on anoptical brightness range.
 27. The mobile device of claim 21 wherein thedisplay screen displays an indication of how much power each suchhardware component or software application is consuming at a particularinstant in time.
 28. The mobile device of claim 21 wherein the displayscreen displays an indication of how much power each such hardwarecomponent or software application is consuming over a defined period oftime.
 29. The battery-operated electronic device of claim 1 wherein theone or more persistent data storage devices store conversion rules forestimating power consumptions by the different software applications,the conversion rules based on estimates of power required to performvarious activities, and wherein determining corresponding amounts ofpower consumed by the different software applications includes using theconversion rules.
 30. The method of claim 8 wherein the determiningincludes using conversion rules that are based on estimates of powerrequired to perform various activities.